Release MEX 0.8.1 - #176

What

Prepare MEX 0.8.1 with clearer project context, practical team handoffs, safer grounding, and a Hub that can serve requests during Graph construction.

• Context shows existing Wiki entities, relationships, direct code groundings, filters, details, and a list alternative. Specs/Workstreams leave primary navigation while existing artifacts and routes remain readable.
• Inbox proposes additions and corrections to existing knowledge through local drafts, Git-shareable Markdown proposals, and explicit approval, retaining evidence and legacy Spec support.
• Relays support open-to-team audiences, including future active Members, recipient-free local drafts, simpler draft saving, clear sharing/eligibility states, and Member reactivation.
• Grounding baseline renewal requires explicit, scoped acceptance. Successful agent exit and moved-symbol repair preserve earlier change evidence.
• Hub Settings and CLI expose checkout-local logging cadence; managed instructions retrieve relevant Timeline notes. Wiki provenance and unknown-file migration classification are tightened.
• Windows fixes narrow CRLF normalization and retain full-width filesystem identity in affected ownership/recovery paths.
• Hub Graph construction uses a disposable Node process while the parent retains validation and publication. Statement reuse, smaller temporary collections, and outer-owned fingerprint transactions reduce avoidable work. This does not add incremental indexing or a peak-memory quota.
• Telemetry adds namespaced CLI outcomes and allowlisted Hub page/action/job events with bounded delivery. A shared random installation UUID, existing scaffold UUIDs, and configured AI-tool names support repeat/shared-project estimates. Events exclude content, paths, queries, names, remotes, and contact details. CLI feedback uses the Hub's voluntary form without an analytics ID.
• Package/lock metadata and capability goldens use 0.8.1. Changelog, release notes, and upgrade guides cover the full release. Translated install guidance is current, with an explicit notice where product descriptions still cover 0.8.0.

Why

0.8.0 exposed unnecessary workflow friction and Graph jobs that could block Hub interaction, including the investigation associated with #140. This release improves those existing workflows while preserving tracked Markdown as canonical and maintenance as an explicit action.

Type of change

• Bug fix
• New feature
• Refactor
• Docs
• CI/Tooling

How to test

• Release-preparation commit dcc95d8: production build, root/Hub typechecks, 82 focused version/capability/CLI/public-API/skill tests, and the packed fresh-install smoke pass. Built CLI reports 0.8.1; public declarations and dependency resolutions are unchanged.
• Prior integrated head 0118536 passed Node 22/24, Windows/macOS, browser, packed-install, and release-performance CI. CI setup removes unused legacy/deb822 Chrome apt sources before unchanged Playwright installation; package verification and test budgets remain intact.
• Final release-preparation CI run 34391072868 passed all required checks on dcc95d8: Node 22/24, Windows/macOS, browser, packed installs, and release performance. The performance gate passed after its automatic fresh-runner confirmation; no implementation or budget changes were needed.
• Detailed verification and phase measurements are recorded in the release plan.

Checklist

• Final release-preparation CI passes
• Compatibility changes documented: new open-to-team Relays use schema v4; teammates must upgrade to 0.8.1 before consuming them. Existing v1–v3 artifacts remain supported; new named handoffs still use v3.
• Tested locally with real installed packages and retained phase-local Hub/Graph probes
• Version, changelog, release notes, and managed-skill upgrade guidance prepared

Nix source-package limitation: its version now follows package.json, but its pre-existing fixed dependency hash needs regeneration and a successful Nix build. Neither is claimed verified by the npm checks. See compatibility guidance.

This PR remains a draft. Merging into main, tagging, and publishing are separate release steps; none has been performed here.

Code-graph changes

• This PR targets main
• Extractor/grammar-specific additions are not part of this release branch's changes.
• Existing LanguageExtractor / FrameworkResolver interfaces are preserved
• Focused storage, lifecycle, grounding, and worker-boundary regressions are included
• Grounding acceptance and maintenance lifecycle changes are intentional; the release branch includes main through bc2d40a.